The ETL job RMB_STG_230_COUNTERPARTY in SAS^® Risk Management for Banking violates the integrity constraint of the Counterparty_Mart staging table by permitting multiple COUNTERPARTY_RK values. The problem can occur even if the data that is loaded in the source tables do conform to the integrity constraints of those tables.

This issue occurs because the ETL job RMB_INT_100_I_COUNTERPARTY does not sufficiently consider the case in which there are multiple instances of a counterparty for different VALID_FROM_DTTM and VALID_TO_DTTM time periods.

The workaround is to remove the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM" from the join condition in SQL Join 2. Then insert a WHERE clause in the SQL join with the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM". That is:

1. Open the job RMB_INT_100_I_COUNTERPARTY:
   
   
   
   
2. Insert a WHERE clause:
   
   
   
   
3. Remove the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM" from the SQL Join:
   
   
   
   
4. Add the condition "COUNTERPARTY.VALID_FROM_DTTM <= &run_date < COUNTERPARTY.VALID_TO_DTTM to the WHERE clause:
   
   
   
   

Operating System and Release Information